-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kafka tombstone message support #16962
Kafka tombstone message support #16962
Conversation
80b8a40
to
4404bb3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
||
waitUntilTableExists(topicName); | ||
|
||
// tombstone message should have all null values except key |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you think a test which verifies that tombstones can be differentiated from messages with all fields set to null
would be useful? It would help us "document" the contract which we talked about so that users can differentiate between tombstones and actual nulls in their messages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test added, we can differentiate these 2 cases by internal message_corrupt field
c05dcd9
to
7353537
Compare
7353537
to
9ae48c4
Compare
@mosabua this would be nice to document on how users can inspect/filter out tombstone messages if they want to. Before this change it lead to query failure. The TL;DR is:
|
Description
Kafka tombstone message support
Additional context and related issues
Release notes
( ) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
(x) Release notes are required, with the following suggested text: